A Practical Approach for Database and Recovery Management System (Oracle, Ms Access)

 

Ankita Agrawal*, Dr. Awadhesh Kumar Sharma

Dept. of Computer Science and Engineering, MMMEC, Gorakhpur  (U.P)

*Corresponding Author E-mail: ankitaagarwal_01@yahoo.com; akscse@rediffmail.com

 

 

ABSTRACT:

The execution of modern database applications requires the co-ordination of number of components such as: the application itself, the DBMS, the operating system, the network and the platform. The interaction of these components makes understanding the overall behavior of the application a complex task. As a result the effectiveness of optimizations are often difficult to predict. Three techniques commonly available to analyze system behavior are empirical measurement, simulation-based analysis and analytical modeling.

 

To verify the effectiveness of the model a validation framework is developed. Database workloads are executed on the flexible Flask architecture on different platforms. Flask is designed to minimize the dependencies between DBMS components and is used in the framework to allow the same workloads to be executed on a various recovery mechanisms. Empirical analysis of executing the workloads is used to validate the assumptions about CPU, I/O and workload that underly MaStA. Once validated, the utility of the model is illustrated by using it to select the mechanisms that provide optimum performance for given database applications.

 

 

 

1. INTRODUCTION:

The database concept has evolved since the 1960s to ease increasing difficulties in designing, building, and maintaining complex information systems (typically with many concurrent end-users, and with a large amount of diverse data). No widely accepted exact definition exists for DBMS. However, a system needs to provide considerable functionality to qualify as a DBMS. Accordingly its supported data collection needs to meet respective usability requirements (broadly defined by the requirements below) to qualify as a database. Thus, a database and its supporting DBMS are defined here by a set of general requirements. Virtually all existing mature DBMS products meet these requirements to a great extent, while less mature either meet them or converge to meet them[1].

 

Database concepts: Database design is done before building it to meet needs of end-users within a given application/information-system that the database is intended to support. The database design defines the needed data and data structures that such a database comprises. A design is typically carried out according to the common three architectural levels of a database (see Database architecture above). First, the conceptual level is designed, which defines the over-all picture/view of the database, and reflects all the real-world elements (entities) the database intends to model, as well as the relationships among them[2].

 

Database migration between DBMSs: A database built with one DBMS is not portable to another DBMS (i.e., the other DBMS cannot run it). However, in some situations it is desirable to move, migrate a database from one DBMS to another. The reasons are primarily economical (different DBMSs may have different total costs of ownership-TCO), functional, and operational (different DBMSs may have different capabilities). The migration involves the database's transformation from one DBMS type to another. The transformation should maintain (if possible) the database related application (i.e., all related application programs) intact. Thus, the database's conceptual and external architectural levels should be maintained in the transformation.[3]

 

Backup and Restore: Backups have two distinct purposes. The primary purpose is to recover data after its loss, be it by data deletion or corruption. The secondary purpose of backups is to recover data from an earlier time, according to a user-defined data retention policy, typically configured within a backup application for how long copies of data are required. Sometimes it is desired to bring a database back to a previous state (for many reasons, e.g., cases when the database is found corrupted due to a software error, or if it has been updated with erroneous data) hence  backup concept is used[4].

 

Database Backup and Migration Systems: A database backup and migration system (DBMS) is a system that allows to migrate and maintain databases, as well as to utilize their data and retrieve information from it. A DBMS defines the database type that it supports, as well as its functionality and operational capabilities. Before data is sent to its storage location, it is selected, extracted, and tested whether that table name present or not. Many different techniques have been developed to optimize the backup procedure. We have developed Database Backup and migration System in an easy and quick manner for the database users by using backup strategy So we call it as Database Backup and Migration  System which delivers via the user interface as desktop application which acting as a Service Provider. By using this technology we can make fast backup and easily migrate database from one platform to another platform. This project has various kinds of users because now days no any place where we don’t use database[5].

 

2. OVERVIEW OF SYSTEM:

2.1.1. Existing System: Coming to the existing system the migration is done by manual process. In the previous system user has only one choice that he can migrate only one data of one platform to another one. By this system we cannot migrate the database of another platform into required platform. Here problem is that at a time we can only migrate the database of one platform into another that was designed to migrate that is if system is designed to migrate access database to the Oracle then we cannot use it for conversion of access to My SQL .The existing system is carries more time to do a piece of work for this reason the ‘Database Backup and Migration System’ is implemented. This is the major advantage of the existing system for migrating the database of one platform to another that is homogeneous solution for heterogeneous problem[4,6,7].

 

2.1.2 Proposed System: Here we aimed to design desktop application for issuing the migration of any database to required database no matter which is that database and where to transfer or migrate. This migration is done by using backup files of required database. Database Backup and Migration System is design to provide for migration of databases in a easy and quick manner to the required databases with the help of backup. So we call it as Database backup and Migration System which delivers via the user  interface as desktop application system which acting as a Service Provider by using this technology we can make fast migration of databases This project has various kinds of users because now a days databases are used everywhere in business, organizations, companies. To perform migration firstly user has to take backup of that required database and then he can easily migrate that database into another platform. These result of the migrated database then checked by the user who has to  used that migrated database. He can view overall migrated database tables. As compared to the manual system, this system is very simple to use and also understandable[5,8,9].

 

Figure: 2.1 Migration workflow as proposed in research

 

Figure: 2.2 Context level diagrams of DBMS

 

 

Figure: 2.3 Data Flow Diagram of DBMS

 

Figure: 2.4 User Process

 

3. METHODOLOGY:

A database backup and migration system (DBMS) is a system that allows to build and maintain databases, as well as to utilize their data and retrieve information from it. It is an database migration tool where xml plays an important role. To implement here we used simple xml where first database is convert into xml file and then into required database. A DBMS defines the database type that it supports, as well as its functionality and operational capabilities. For managing a complex project, it is fortunate to have at least a checklist of things to do. Here xml is used as a intermediate language. Better still, a complete process model, covering the whole workflow. This should include all necessary steps, covered to an appropriate level of granularity (neither too abstract, covering everything important, nor too detailed, remaining generic enough to be useful for various scenarios).By using xml it is easily convert one database into another it act as a intermediately language. This process model shall provide a workflow able to minimize risk, keep the project on budget, deliver in due time, keep downtime to a minimum and in case of failure, be able to return to the source system. The goal is to switch from one database system to another that will cover the same functionality, containing the same data and semantics, without decrease in performance or reliability. I proposed a migration workflow that mixes asset-centered with activity-centered database migration process models (while leaning to the asset-centered side):

 

1.     It analyse the whole source system .

2.     Migrate the Source database management system software.

3.     Migrate the schema.

4.     Analyze the data and provide conversions. Transfer test data.

5.     Test the migrated schema with the test data.

6.     Migrate the database.

7.     Migrate the database systems infrastructure.

8.     Cut-over: Implement the data migration.

9.     Final testing and evaluation.

 

4. EXPERIMENTAL RESULT:

Figure 4.1; Login

 

Figure 4.2: Main Window

 

Figure 4.3: Back Up File

 

Figure 4.4: XML File

 

Figure 4.5: Import Database

 

Figure 4.6: Option for Displaying Table

 

Figure 4.7: Data in Tabular form

 

Figure 4.8 Import Database

 

Figure 4.9 One Table is imported

 

Figure 4.10 Select backup

 

Figure 4.11 Backup Removed

 

Figure 4.12 Interface

 

4. CONCLUSION AND FUTURE SCOPE:

Normally conventional system we use maximum manual applications. It consumes lots of time and paper. But this system totally System based, it means that user can enter into the system very easily. They can view the details of the database that are used in this project. This system is totally user friendly and timesaving and cost effective system. All the modules are designed in a way that a layman can understand the system very easily. User shall access any data from any database in very minimum amount of time. The Database Backup and Migration System is developed using different type of database are MySQL, Oracle and Ms-Office fully meets the objectives of the system for which it has been developed. The system is operated at a high level of efficiency and user in industrial area or corporation area with the system understands its advantage. The system solves the problem. It was intended to solve as requirement specification. The future enhancement that can be done with this database migration system is that now this system is not online application after some further implementation this system can be used as online application. This System is developed for daily  in schools, colleges , business and in industry for the database migration but in future this system can be used for daily and we will allow this system to implement some feature in future if it require.With full access to the Java platform, running from the server in a secure manner, the application possibilities are almost limitless. When JAVA used along with Enterprise JavaBeans technology, e-commerce and database resources then it can meet to enterprise's needs for secured web based transactions in an open platform. J2EE technology as a whole makes it easy to develop, deploy and use web server applications instead of mingling with other technologies such as CGI and ASP. There are many tools for facilitating quick web software development and to easily convert existing server-side technologies to JSP and Servlets.

 

5. REFERENCES:

1.       Xiaofeng Wang, Liang Cao, Shangping Wang, Yaling Zhang, ID- Based Convertible Limited (Multi-) Verifier Signature Scheme, 2008 International Conference on Computer Science and Software Engineering. 774-777.

2.       D.B. Ojha et al, /(IJCSIT) International Journal Of  Computer Science and Information Technologies, Vol. 2(1), 2011, 465-468 468

3.       X. Cheng, L. Guo , X. Wang, An Identity- based Mediated Signature Scheme from Bilinear Pairing, International Journal of Network Security, 2(1) : 29-33, 2006.http://isrc.nchu.edu.tw/ijns.

4.       whitepapers.zdnet  : http://whitepapers.zdnet.com/abstract.aspx?docid=122052

5.       swissql:http://www.swissql.com/products/sqlone consolejava/sqlone-consolejava.html

6.       mssql2pgsql : http://sf.net/projects/mssql2pgsql

7.       mysql:http://www.mysql.com/products/tools/migration-toolkit/,

8.       http://dev.mysql.com/doc/migration-toolkit/en/

9.       sqlkit.htm : http://convert-in.com/sqlkit.htm

 

 

© EnggResearch.net All Right Reserved